-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: upgrade zktrie to v0.6.0 #403
Conversation
Some unittests which hard-coded a expected state hash are pending for update |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am a little concerned with all the panics, can't we just return errors?
the new poseidon hash code is frozen. Can @mask-pp help to generate some traces in traces repo (not all traces need like bridge if it is too complex, several traces like swap transfer sushi will be ok) so we can have more tests? |
Everything for new hash scheme is done. The endianess issue would be resolved in l2geth, not zktrie module, with another PR |
Agreed, but we can leave this as a refactoring step after the release. |
This PR upgrade zktrie to v0.6.0
It should be tested against trace-dumper
- [ ] update zktrie to v0.6.1 (the endianness of zktrie key in storage layer would be reversed)Should not be merged until the depended zktrie has been stable